Methods and system for fast session establishment between equipment using H.324 and related telecommunications protocols

ABSTRACT

Methods of establishing multimedia telecommunication (a multimedia “call”) between equipment (“terminals”). More particularly, the invention provides methods for reducing the time required to establish calls between terminals that implement the ITU-T H.324 Recommendation and other Standards and Recommendations derived from or related to this such as the 3G-324M recommendation developed and adopted by the Third Generation Partnership Projects (3GPP and 3GPP2). More specifically, it relates to: (i) a method and apparatus for concatenating the H.245 messages that are required to pass between the terminals at the start of the call to establish the capabilities of both terminals and agree on the type and format of media and data to be exchanged; (ii) a method and apparatus for using non-standard H.245 messages or standard H.245 messages with non-standard fields to accelerate such establishment; (iii) a method and apparatus of informing each terminal of the capabilities of the other and proposing the type and format of media and data to be exchanged by means of any user-defined fields that are inserted in the call signaling protocol that is used for bearer establishment prior to the start of the H.324 stage of the call; and (iv) a method and apparatus of informing each terminal of the capabilities of the other and proposing and accepting the type and format of media and data to be exchanged by means of a burst of bits optionally encoded for error control on the bearer channel as soon as it is desired, preferably as the first information transmitted on the bearer channel.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation in part of U.S. application Ser. No.10/732,917, filed Dec. 9, 2003 (Attorney Docket Number 021318-0001710),which claims priority to U.S. Provisional No. 60/433,252 filed Dec. 12,2002, which is incorporated by reference herein.

COPYRIGHT NOTICE

A portion of this application contains computer codes, which are ownedby Dilithium Networks Pty Ltd. All rights have been preserved under thecopyright protection, Dilithium Networks Pty Ltd. ©2003.

BACKGROUND OF THE INVENTION

The present invention relates generally to methods of establishingmultimedia telecommunication (a multimedia “call”) between equipment(“terminals”). More particularly, the invention provides methods forreducing the time required to establish calls between terminals thatimplement the ITU-T H.324 Recommendation and other Standards andRecommendations derived from or related to this such as the 3G-324Mrecommendation developed and adopted by the Third Generation PartnershipProjects (3GPP and 3GPP2). Merely by way of example, the invention hasbeen applied to the establishment of multimedia telecommunicationbetween 3G-324M (H.324M based protocol) multimedia handsets on a mobiletelecommunications network, and between 3G-324M multimedia handsets andH.323 based terminals on a packet network using a Multimedia Gateway tomediate between the protocols used at each endpoint, but it would berecognized that the invention may also include other applications.

H.324 is an International Telecommunication Union (ITU) protocolstandard for multimedia communication over general switched networks(GSTN). H.324M is an extension of H.324 for operations over mobilenetworks, and 3G-324M is a recommendation by the third generationpartnership program (3GPP) defining adaptation of H.324M for use within3GPP and also adopted by 3GPP2. We call H.324-like equipment devices andsystems employing protocol based or derived from H.324. H.324-likeequipment can connect to other H.324-like equipment via switchingcenters and to other non-H.324-like equipment through multimediagateways. An example of a non-H.324-like equipment is an H.323equipment. H.323 is an International Telecommunication Union protocolStandard for multimedia communication over non-guaranteed bandwidthpacket networks. An H.323-like equipment is an equipment that employs aprotocol based or derived from the H.323 protocol.

Without any loss of generality, we will use the term “H.324” to indicateH.324-like equipment including H.324M and 3G-324M equipment and “H.323”to indicate H.323-like equipment.

Also without any loss of generality we use the term “equipment” toindicate either a user end equipment such as a handset, or network endequipment such as a switch or gateway. The term “equipment” covers themeaning of “entity”. We also use the terms “equipment” and “terminal”interchangeably, and they both indicate the same meaning in the presentdocument.

If a call is made between equipments which are an embodiment of theH.324, H.324M or 3G-324M, the first stage of the call is to establish anend-to-end bearer between the equipments. This stage is called CallSignaling and is outside the scope of H.324, except where modems and theGeneral Switched Telephony Network are used. The second stage of thecall is to establish the H.324 session, to provide a means oftransporting video, audio and data between the equipments in a formatthat is known to, and supported by the equipments. In order to do thisH.324M makes use of two further ITU-T Recommendations.

The first of these Recommendations used is H.223 “Multiplexing protocolfor low bit rate multimedia communication”. H.223 specifies aframe-oriented multiplexing protocol which allows the transfer of anycombination of digital voice, video and data (e.g. command and control)information over a single communication link. The H.223 may have anumber of modes of operation, specified in Annexes A, B and C of theH.223 Recommendation that are intended to provide increased resiliencein the presence of errors. These are also known as Mobile Levels 1, 2and 3. H.223 without the application of any of these Annexes is alsosometimes referred to as operating at Mobile Level 0 (base-line). H.324has the concept of Logical Channels which is a way of providing virtualchannels over the circuit switched link. The role of the multiplexer isto combine (multiplex) parts of the data chunks written on the logicalchannels into frames known as a Multiplexer Protocol Data Unit(MUX-PDU). Logical Channel 0 is always available and is used for Commandand Control. Data (voice, video, command and control and other generaldata) is passed to/from the H.223 multiplexer through bitstream chunkscalled service data units (SDUs). Before being multiplexed, thesedifferent SDUs go through Adaptation Layers where extra information maybe added for purposes such as error detection, sequence numbering andretransmission requests.

The second of these Recommendations is H.245 “Control protocol formultimedia communication” which specifies the syntax and semantics ofterminal information messages as well as procedures to use them forin-band negotiation at the start of or during communication. Themessages cover receiving and transmitting capabilities and preferences,logical channel signaling and control and indication. The messages thatare specified in H.245 are expressed in the ITU-T Abstract SyntaxNotation (ASN.1) and can be classified as of Request, Response, Commandor Indication type. H.245 messages are encoded according to the ASN.1standard before being transmitted. When a terminal sends an H.245message of type Request it requires that an appropriate message of typeResponse is sent by the remote terminal. If the Response (sometimesreferred to as an Ack for Acknowledgement) is not received within acertain time, the sending terminal will re-transmit the Request or takeanother appropriate action if no response has been received for repeatedRequests. Re-transmission of requests may occur a number of times. Manyof the H.245 messages associated with call setup are of the Requesttype.

H.245 also requires a reliable link layer for proper operation. Theprincipal means of providing this, specified in Annex A of H.324, is touse the Simple Retransmission Protocol (SRP) or the Numbered SimpleRetransmission Protocol (NSRP), in which one or more H.245 messages,known collectively as a MultimediaSystemControl PDU and in the presentdocument as an H.245 PDU, are formed into SRP Command Frames prior tosending, and the receiving terminal must send an SRP Response Frame(Sometimes referred to as an SRP Ack) to acknowledge correct receipt ofan SRP Command Frame. No further H.245 messages may be sent by aterminal until the SRP Ack for the last message has been received.

The combined effect of the requirement to send an H.245 Response messagefor each H.245 Request Message received, and of the need to receive anSRP Ack for every SRP Command Frame sent means that a single H.245Request message may take some time to be conveyed successfully. Thecommunication involved in sending an H.245 Request message from oneterminal (A) to another (B), and getting an H.245 Response (Ack) messageback is shown in FIG. 1A, which also shows the SRP Command Frames (SRPCF) and SRP Response Frames (SRP RF or SRP Ack) involved when singleH.245 messages are formed into single SRP Command Frames. The H.324standard allows for multiple H.245 messages to be concatenated into asingle SRP Command Frame; however this capability is often notimplemented, in which case such terminals may respond only to the firstH.245 message encountered in an SRP Command Frame. In some cases,terminals which do not support this capability may malfunction uponreceipt of an SDU containing multiple H.245 requests or responses.

We will refer to the sequence of H.245 Request and Response shown inFIG. 1A as a “round trip” and the time associated with completing it asa “round trip delay”.

The key steps involved in setting up and connecting a typical H.324 callare as follows:

-   -   1. Call signaling (bearer establishment)—outside the scope of        H.324. Normally a modem connection if GSTN, through ISDN, or        signaling through mobile switching centers in the mobile case.    -   2. Mobile level detection (MLD)—Where a common Mobile Level is        agreed on between equipments. This step is performed by H.324        equipment that supports mobile extensions such as H.324M and        3G-324M equipment.    -   3. Terminal Capability Exchange (TCS)—H.245 Messaging    -   4. Master Slave determination (MSD)—H.245 Messaging    -   5. Open/Close Logical Channels (OLC)—H.245 Messaging    -   6. Multiplexer Table Entries Exchange (MTE)—H.245 Messaging

Steps (3) to (6) are performed using a sequence of H.245 Request andResponse messages as described above and illustrated in FIG. 1A. Thefull sequence of Request and Response messages involved in an H.324 callis shown in FIG. 1B. Note the order of steps (5) and (6) above can beinterchanged. It should be noted that Steps (3) to (6) relate toprocedures that are defined by underlying state machines that are alsoknown as Signaling Entities. The relevant signaling entities are:

-   -   1. Capability Exchange Signaling Entity (CESE)    -   2. Master Slave Determination Signaling Entity (MSDSE)    -   3. Logical Channel Signaling Entity (LCSE)    -   4. Multiplex Table Signaling Entity (MTSE)

Once these steps have completed, media (video, audio and data) can flowbetween the terminals. Note the H.245 messages flow on the LogicalChannel 0 which as previously described is predefined and carried by themeans of the multiplexer predefined Multiplex Table Entry 0. Once otherMultiplex Table Entries have been exchanged these can also be used inconjunction with H.245 messages.

The key steps above are often handled sequentially; however this resultsin as many as ten H.245 message round trip delays in order to establishan H.324 session with two logical channels in each direction. Inaddition, the SRP scheme (or Numbered version —NSRP, in cases where themobile level is greater than zero) used for H.324/H.245, which requiresan SRP message to be received by the endpoint for every message sent,prior to sending any other message, regardless of whether it isassociated with the same Signaling Entity or not, further limits thescope to pipeline messages on the network, making call setup slower thanif this were not the case. SRP messages are not shown in FIG. 1B.

For H.324M, the Terminal Capabilities Set request (TCS) step describedabove and shown in FIG. 1B is preceded by a mobile leveldetection/multiplexer synchronization phase. This consists of eachterminal transmitting a repeating pattern of bits (flags) that indicatethe highest Mobile Level that it operates at. Each terminal examines theflags that it is receiving. If these flags represent a lower MobileLevel then the terminal drops down to the same lower level. When bothterminals are transmitting the same flag sequence this step completes.

Arising from the set of procedures described above that are required totake place to establish an H.324M call, when a call is made from aterminal which is an embodiment of the H.324 it is prone to suffer fromlong call setup time, which is the interval between the time that thecall signaling is initiated to the time that the exchange of voice andvideo commences between an H324-like end-point (H.324, H.324M or3G-324M) and other terminals whether H.324-like or not.

The ITU Recommendation H.323 uses H.245 in a similar manner to H.324 forsignaling command, control and indication messages related to a call.Unlike H.324, H.323 is equipped with a number of features to speed upthe call setup time between H.323 equipment. Similar techniques existfor the IETF Session Initiation Protocol (SIP) protocol.

Thus there exists a need for techniques to speed up the call setupbetween H.324 like terminals and other terminals either of the H.324type directly, or terminals such as H.323 via multimedia gateways. Thedifferences between the H.324 protocol (and its extensions such asH.324M and 3G-324M) and H.323 and other protocols mean that additionalaspects need to be considered when introducing call establishmentspeed-up techniques for H.324-like terminals. Such differences includethe information about mobile levels where they are used and themessaging and information related to the H.223 multiplexer such as itsmultiplex table entries, adaptation layers and so on.

BRIEF SUMMARY OF THE INVENTION

According to the present invention, techniques for telecommunicationsare provided. More particularly, the invention provides methods forreducing the time required to establish calls between terminals thatimplement the ITU-T H.324 Recommendation and other Standards andRecommendations derived from or related to this such as the 3G-324Mrecommendation developed and adopted by the Third Generation PartnershipProjects (3GPP and 3GPP2). More specifically, it relates to: (i) amethod and apparatus for concatenating the H.245 messages that arerequired to pass between the terminals at the start of the call toestablish the capabilities of both terminals and agree on the type andformat of media and data to be exchanged; (ii) a method and apparatusfor using non-standard H.245 messages, or standard H.245 messages withnon-standard fields to accelerate such establishment; (iii) a method andapparatus for informing each terminal of the capabilities of the otherand proposing the type and format of media and data to be exchanged bymeans of any user-defined fields that are available in the callsignaling protocol that is used for bearer establishment prior to thestart of the H.324 stage of the call; and (iv) a method and apparatus ofinforming each terminal of the capabilities of the other and proposingthe type and format of media and data to be exchanged by means of aburst of bits optionally encoded for error control on the bearer channelas soon as it is desired, preferably as the first informationtransmitted on the bearer channel.

These methods may be used separately or severally to reduce the timethat is taken from the point when a user requests the establishment of acall to the point where media starts to be exchanged between theterminals. Merely by way of example, the invention has been applied tothe establishment of multimedia telecommunication between 3G-324M(H.324M based protocol) multimedia handsets on a mobiletelecommunications network, and between 3G-324M multimedia handsets andH.323 based terminals on a packet network using a Multimedia Gateway tomediate between the protocols used at each endpoint, but it would berecognized that the invention may also include other applications.

According to the present invention, techniques for reducing the numberof sequential steps that are required to establish an H.324-like callare provided through a number of methods that may be used separately orseverally.

At least four types of methods are described to reduce the number ofsteps. We call these methods Type I, II, III, and IV and we number themfor ease of reference in the present document. Such methods may becombined or used with conventional techniques depending upon theembodiment. One of ordinary skill in the art would recognize manyvariations, alternatives, and modifications.

In a specific embodiment, the methods are as follows:

-   -   1. Type I: Concatenation of H.245 messages so the number of        standard SRP/NSRP command messages is reduced, in order to start        media communication.    -   2. Type II: Incorporation of H.245 Non-Standard messaging        capabilities to incorporate information about the equipment        involved in the call so the number of H.245 and SRP/NSRP message        exchanges are minimized, in order to start media communication.    -   3. Type III: Incorporation of equipment preferences information        in the call signaling protocol exchange as to eliminate the need        for further information exchange between the equipment in order        to start media communication following call signaling.    -   4. Type IV: Incorporation of equipment preferences information        in the first burst of bits transmitted by the equipment on the        bearer as soon as the bearer is available for data transmission.        The burst of bits could represent the preferences information,        an encrypted version of it, or an encoded version of it where        the encoding is meant for protection against errors due to        interference or other conditions. The burst of bits may be        repeated a number of times to increase the likelihood of another        entity supporting Type IV to detect the information, and to        avoid issues with synchronisation of the start of bearer data        transmission/transport.

In each case the method provides a means to revert to the behavior of aterminal conforming with the H.324 standard.

Type I: Speed-Up by Concatenation of H.245 Messages in SRP/NSRP CommandFrames

This method exploits the capability to concatenate multiple H.245messages within a single SRP/NSRP (H.245 PDU) Command Frame as a mean toreduce the number of H.245, SRP/NSRP messages and associated round-tripdelays. The H.245 messages have to be concatenated in a way as not toviolate dependencies.

The usage of H.245 within H.324 allows equipment to concatenate multipleH.245 elements into a single PDU, thus avoiding the need to use tworound trips for each request/response pair due to the need for anSRP/NSRP response to be received for each H.245 PDU before the next PDUis allowed be transmitted.

The method uses concatenated H.245 to send multiple H.245 messages, eachoriginating from different Signaling Entities that have no dependencieson each other, within a single H.245 PDU.

Interoperability with equipment that do not support concatenated H.245is achieved by noting that such equipment ignore the second andsubsequent H.245 elements in a PDU, so will not send any required H.245Response messages if the ignored message is an H.245 Request message.Therefore the first concatenated H.245 PDU sent should contain at leasttwo Request messages, where the first message must be a Request. If onlythe Ack for the first message is received, the sending equipment willretransmit those Requests and any other messages that have not beenacknowledged, and in doing this and in sending any and all subsequentH.245 messages should revert to sending only a single H.245 message ineach subsequent H.245 PDU. If responses to all H.245 messages in thefirst H.245 PDU are received, the sending equipment can continue to useconcatenated messages. The use of this technique will reduce the numberof round trip delays if concatenated messages are supported. This methoddoes not define any protocol elements additional to those alreadyallowed and defined by the H.245 and H.324 standards. It can beconsidered to be utilizing the existing protocols in a smart fashion,rather than an extension to it.

Preferably, the present invention provides a method of initiating a callbetween users with reduced call set-up times using one or moretelecommunication networks. The method is provided between at least apair of H.324-like terminals coupled to the one or moretelecommunication networks. The method includes transmitting a callsignaling message from a first terminal to a second terminal through atelecommunication network to initiate a call, establishing a bearerchannel between the first terminal and the second terminal once the callsignaling message has been received by the second terminal, anddetermining a common mobile level. As used herein and throughout thespecification, the term “first terminal” and “second terminal” areprovided for illustrative purposes only. Functionality associated witheach of these terminal can be interchanged, combined, or the like,without departing from the scope of the claims defined herein.Additionally, the method includes determining two or more H.245 messagesassociated with set up parameters for an initial predetermined mode ofoperation, concatenating the two or more H.245 messages into one SRPcommand frame according to a predetermined size of the SRP commandframe, and transmitting the SRP command frame including the two or moreH.245 messages from the first terminal to the second terminal through atelecommunication network. Moreover, the method includes transmitting anSRP acknowledge message by the second terminal once the SRP commandframe has been received by the second terminal, processing at least thetwo or more H.245 messages during a predetermined time period, andestablishing the initial predetermined mode of operation between thefirst terminal and the second terminal through the bearer channel.

According to another embodiment, the present invention provides acomputer-readable medium including instructions for initiating a callbetween users with reduced call set-up times using one or moretelecommunication networks. The computer-readable medium is providedbetween at least a pair of H.324-like terminals coupled to the one ormore telecommunication networks. The computer-readable medium includesone or more instructions for transmitting a call signaling message froma first terminal to a second terminal through a telecommunicationnetwork to initiate a call, one or more instructions for establishing abearer channel between the first terminal and the second terminal oncethe call signaling message has been received by the second terminal, andone or more instructions for determining a common mobile level.Additionally, the computer-readable medium includes one or moreinstructions for determining two or more H.245 messages associated withset up parameters for an initial predetermined mode of operation, one ormore instructions for concatenating the two or more H.245 messages intoone SRP command frame according to a predetermined size of the SRPcommand frame, and one or more instructions for transmitting the SRPcommand frame including the two or more H.245 messages from the firstterminal to the second terminal through a telecommunication network.Moreover, the computer-readable medium includes one or more instructionsfor transmitting an SRP acknowledge message by the second terminal oncethe SRP command frame has been received by the second terminal, one ormore instructions for processing at least the two or more H.245 messagesduring a predetermined time period, and one or more instructions forestablishing the initial predetermined mode of operation between thefirst terminal and the second terminal through the bearer channel.

Type II: Speed-Up using H.245 Non-Standard Messages/Data Elements

A second method that is the subject of the present invention forreducing the number of sequential steps that are required to establishan H.324-like call proposes the use of Non-Standard messagingcapabilities of the H.245 protocol. H.245 allows a number of ways ofadding non-standard extensions. There are a number of ways to addnon-standard messages, or data elements of existing messages, in H.245in order to speed up the call. The most interesting of these is the useof a nonstandard Capability within the H.245 TerminalCapabilitySetmessage and a NonStandardMessage H.245 Response message. These messagescan be used to signal that the calling equipment is capable of operatingin a particular way, and to provide proposals and preferences to theremote terminal relating to Master Slave Determination, LogicalChannel(s) to be opened and Multiplexer Table Entries embedded withinthese non-standard extensions to accelerate call set-up. If the remoteterminal supports this method, it will signal the calling terminal usinga non-standard extension which will also indicate that it accepts, andmay also propose modifications or provide other information, includingfor example the Multiplexer Table Entries that it is using.

If the called terminal does not support this method, it will simplyignore the non-standard extension and not respond with the non-standardresponse, but a standard response. The call will then proceed as for astandard H.324-like call. The Type II method does not requirenon-supporting terminals to handle Type I method.

Preferably, the invention provides a method of initiating a call betweenusers with reduced call set-up times using one or more telecommunicationnetworks. The method includes transmitting a call signaling message froma first terminal to a second terminal through a telecommunicationnetwork to initiate a call and establishing a bearer channel between thefirst terminal and the second terminal once the call signaling messagehas been received by the second terminal. The method also includesdetermining a common mobile level for operation. The method provides oneor more custom Non-Standard H.245 messages or custom Non-Standard fieldsin standard H.245 messages. The one or more custom H.245 messages orcustom Non-Standard fields are associated with one or more set upparameters for an initial preferred or predetermined mode of operation.Additionally, the method includes transmitting the one or more customNon-Standard H.245 messages or custom Non-Standard fields in standardH.245 messages from the first terminal to the second terminal,transmitting a custom Non-Standard response message associated with theone or more custom Non-Standard H.245 messages or custom Non-Standardfields from the second terminal to the first terminal, and processingthe one or more custom H.245 messages or custom Non-Standard fieldsduring a predetermined time period. Moreover, the method includesestablishing the initial predetermined mode of operation between thefirst terminal and the second terminal through the bearer channel basedupon at least one or more of the custom H.245 messages or customNon-Standard fields.

According to another embodiment, the present invention provides acomputer-readable medium including instructions for initiating a callbetween users with reduced call set-up times using one or moretelecommunication networks. The computer-readable medium is providedbetween at least a pair of H.324-like terminals coupled to the one ormore telecommunication networks. The computer-readable medium includesone or more instructions for transmitting a call signaling message froma first terminal to a second terminal through a telecommunicationnetwork to initiate a call, one or more instructions for establishing abearer channel between the first terminal and the second terminal oncethe call signaling message has been received by the second terminal, andone or more instructions for determining a common mobile level foroperation. Additionally, the computer-readable medium includes one ormore instructions for providing one or more custom Non-Standard H.245messages or custom Non-Standard fields in standard H.245 messages. Theone or more custom H.245 messages or custom Non-Standard fields areassociated with one or more set up parameters for an initialpredetermined mode of operation. Moreover, the computer-readable mediumincludes one or more instructions for transmitting the one or morecustom Non-Standard H.245 messages or custom Non-Standard fields instandard messages from the first terminal to the second terminal, one ormore instructions for transmitting a custom Non-Standard responsemessage associated with the one or more custom Non-Standard H.245messages or custom Non-Standard fields from the second terminal to thefirst terminal, and one or more instructions for processing the one ormore custom H.245 messages or custom Non-Standard fields during apredetermined time period. Also, the computer-readable medium includesone or more instructions for establishing the initial predetermined modeof operation between the first terminal and the second terminal throughthe bearer channel based upon at least one or more of the custom H.245messages or custom Non-Standard fields.

Type III: Speed-Up by Incorporation of Equipment Preferences in CallSignaling Phase

A third method for reducing call set up times for H.324 terminalsproposes passing information during the call signaling phase (bearerestablishment) where it is possible to embed user-defined informationinto the bearer establishment protocol. This method allows an H.324-likecalling equipment to specify equipment preferences or predeterminedmodes in terms of media communication and the underlying configurationsfor the multiplexer and the logical channels. There are a number of waysto represent such preferences including preference codes (numeric oralpha-numeric string representing pre-defined preference configuration)and explicit preferences expressed in a format such as the ITU-TAbstract Syntax Notation (ASN.1) format. We call these preferences(coded or explicit) profiles. In the case of explicit preferences orprofile, a list of profiles can be transmitted as part of the bearersetup signal or message. A profile (coded or explicit) specifies exactvalues for the all aspects of the multiplexer and H.245 channelsnecessary to set up a call. For example, the Mobile Level, Master SlaveDetermination request parameters, media formats for each logical channeland the multiplexer table entries for each logical channel must bedefined. The answering equipment then selects the profiles to use inuser-defined information embedded in the bearer establishment (callsignaling) signal or message. This allows the terminals to exchange theparameters of the H.245 channel at the time the called equipment acceptsthe call, rather than requiring multiple round trips after the call isaccepted.

The bearer establishment (call signaling) is typically specific to thenetwork where the H.324-like equipment is being used. In the context of3G-324M, the call signaling uses an ITU-T Q.931-like call signalingprotocol that allows the incorporation of the preference informationmessages. The Q.931 allows for the incorporation of user-definedinformation in the protocol messages. Q.931 signaling can be complex,but for the purpose of our description here it can be simplified to twomessages. A “Setup” Q.931 message containing the calling partyinformation and other parameter is transmitted from the callingequipment to the called terminal. The called terminal will respond witha “Connect” message to answer the call (e.g. user pressed the answerbutton). In this context the H.324-like equipment preferences areincorporated in the “Setup” message transmitted by the callingequipment. As mentioned earlier the preference messages can beincorporated in the user defined part of the Q.931 message. When thecalled terminal answers the call by transmitting the “Connect” Q.931message, it incorporates its preferred mode of operation in the userdefined field of its “Connect” response message. The Setup and Connectmessages are described further in the ITU-T Q.931 Recommendation and inthe 3GPP technical specification documents. Note that the 3GPP2equivalent documents exist for the CDMA counterpart of the WCDMA 3GPP.

In the case of ISDN networks (e.g. H.324 over ISDN) and networkssignaled using SS7 protocols, a configuration similar to that describedabove for 3GPP can be used.

In the case of GSTN networks, the call signaling protocols such as V.8,and V.8bis can be augmented to incorporate equipment preference codes.

Ability to utilize coded or explicit preferences overcome somelimitations that call signaling protocols may have on the amount ofuser-defined information that can be included in their messages orsignals.

Preferably, the present invention provides a method of initiating a callbetween users with reduced call set-up times using one or moretelecommunication networks. The method includes providing one or morepreferences for a call associated with a first terminal (e.g., handset,gateway, and other equipment) and a second terminal (e.g., handset,gateway, and other equipment). The one or more preferences areassociated with an initial mode of operation for the call between thefirst terminal and the second terminal. The method also includesprocessing the one or more preferences as a Custom Message (e.g., userdefined based upon preferences) and embedding the Custom Message in apredetermined field of a call initiation message. The method transfersthe Custom Message from the first terminal to the second terminalthrough a telecommunication network using call signaling and processesthe Custom Message by the second terminal. The method includestransferring a Custom Response Message by the second terminal using acall signaling response message to indicate to the first terminal theinitial mode of operation and exchanging information between the firstterminal and the second terminal after the initial mode of operation hasbeen established.

Note that this method of incorporating equipment preference modes ofoperation in the call signaling is particularly efficacious when used inconjunction with H.323 fast connect in the context of an H.324/H.323gateway that mediates calls between H.324-like and H.323-like equipment,respectively. It is similarly efficacious when used in the context of anH.324/SIP gateway that mediates calls between H.324-like and SIPequipment.

According to another embodiment, the present invention provides acomputer-readable medium including instructions for initiating a callbetween users with reduced call set-up times using one or moretelecommunication networks. The computer-readable medium is providedbetween at least a pair of H.324-like terminals coupled to the one ormore telecommunication networks. The computer-readable medium includesone or more instructions for providing one or more preferences for acall associated with a first terminal and a second terminal. The one ormore preferences are associated with an initial mode of operation forthe call between the first terminal and the second terminal.Additionally, the computer-readable medium includes one or moreinstructions for processing the one or more preferences as a CustomMessage, one or more instructions for embedding the Custom Message in apredetermined field of a call initiation message, and one or moreinstructions for transferring the Custom Message from the first terminalto the second terminal through a telecommunication network using callsignaling. Moreover, the computer-readable medium includes one or moreinstructions for processing the Custom Message by the second terminal,one or more instructions for transferring a Custom Response Message bythe second terminal using a call signaling response message to indicateto the first terminal the initial mode of operation, and one or moreinstructions for exchanging information between the first terminal andthe second terminal after the initial mode of operation has beenestablished.

Type IV: Speed-Up by Incorporation of Equipment Preferences in FirstData Burst on Bearer Channel

Another method for speeding up the call setup is by communicating theEquipment Preferences information described in Type III above on thebearer channel instead of the signalling channel. The EquipmentPreferences information can be embedded in an ASN.1 encoded message orusing other type of syntax. The message can be further encoded for noiseimmunity purposes using error control techniques to improve immunityagainst data corruption due to air-interface of communication channelconditions. The Equipment Preference information can be transmitted onthe bearer channel as soon as it is established, and may be repeated anumber of times. We call the preferences message transmitted by thecaller terminal (entity that originated the call) the Caller AF4 Requestand the message transmitted by the answerer terminal the Answerer AF4Request. The answerer message may contain preferences or may be empty.Once the answerer terminal detects the Caller AF4 Request, it analysesthe request and transmits an Answerer AF4 Response which incorporatesthe accepted preferred mode. As soon as the Caller detects the AnswererAF4 Response it can start transmitting media according to the acceptedpreference mode. The Caller needs to be able to accept media accordingto the preferences it indicated in the Caller AF4 Request as it istransmitting the request. The Answerer needs to be able to accept mediaas it is transmitting its response. The Answerer (called) terminal alsotransmits an Answerer Request message when the bearer is available. TheAnswerer Request message could incorporate Equipment Preferences.However for the purpose of speeding up the session setup time, theCaller may ignore the Answerer Request message and simply transmit anempty Response or even not transmit a response. Therefore as bothterminals would transmit their request and their response, once thePreferences are detected and decoded correctly to yield the computerprogram recognizable description, the terminals can automatically switchto the Preferred mode of operation without having to undergo furthernegotiation. Note that standard operations such as mobile leveldetection and H.245 procedures can be performed at a later time.

Note that for the purpose of avoiding conflict and speeding up thesession setup time, the Answerer entity is the entity taking control ofthe decision, in that, the Answerer terminal needs to respond to theCaller proposed Equipment Preferences and ignore the response thatCaller terminal transmits to the Answerer Request.

Another aspect to be considered is the framing of the AF4 Request andResponse messages. In order to facilitate the detection of thesemessages (whether encoded for noise immunity or not) in the bitstream onthe bearer, the messages can be framed using a sequence of one or morebyte-codes. The framing sequences would not be involved in the errorcontrol coding if used. The longer the framing sequence the betterprotection of the message is achieved in the presence of noise.

If one of the terminals does not support this mode of sessionestablishment speed-up, or AF4 Response is not received, or there isconflict with the AF4 modes supported by the terminals, then anothertype of speed-up technique can be tried until a type is recognized orthe terminals would proceed with the base-line mode of operation(without speed-up methods).

In a specific embodiment, the present invention provides a system forprocessing a call between users with reduced call set-up times using oneor more telecommunication networks. The system has one or more memories,which may be in a single device or multiple devices. The memory ormemories include various computer codes that carry out the functionalitydescribed herein. The codes can be in software, hardware, or acombination of these, depending upon the embodiment. Code is directed toproviding one or more preferences for a call associated with a firstterminal and a second terminal. Preferably, the one or more preferencesare associated with an initial mode of operation for the call between afirst terminal and a second terminal. Code is directed to processing theone or more preferences as a Custom Message and code is directed toestablishing a bearer channel between the first terminal and the secondterminal. The system also has code directed to transferring the CustomMessage from the first terminal to the second terminal through atelecommunication network using the bearer channel. Depending upon theembodiment, other computer code can exist to carryout the functionalitydescribed herein.

The objects, features, and advantages of the present invention, which tothe best of our knowledge are novel, are set forth with particularity inthe appended claims. The present invention, both as to its organizationand manner of operation, together with further objects and advantages,may best be understood by reference to the following description, takenin connection with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a diagram useful in illustrating the communications that flowbetween two H.324 terminals when an H.245 Request message is sent fromone terminal to the other;

FIG. 1B illustrates session Set-up for a call between H.324-likeequipment. Note in this case unidirectional video channels are used(e.g. video over adaptation layer AL2 of the H.223 multiplexer).

FIG. 2 illustrates an embodiment of the method of using concatenatedH.245 between two H.324 terminals to reduce connection times for H.324calls;

FIG. 3 illustrates an embodiment of the method of using non-standardextensions of H.245 messages to reduce connection times for H.324 calls;

FIG. 4 illustrates an embodiment of the method of using bearer “user”information to reduce connection times for H.324 calls;

FIG. 5 illustrates an embodiment of the method of using bearer “user”information to reduce connection times for calls between an H.324terminal and an H.323 terminal using a gateway;

FIG. 6 illustrates an embodiment of the ASN.1 Syntax description forType II Request;

FIG. 7 illustrates an embodiment of the ASN.1 Syntax description forType II Response;

FIG. 8 illustrates an embodiment of the ASN.1 Syntax description forType III Request;

FIG. 9 illustrates an embodiment of the ASN.1 Syntax description forType III Response;

FIG. 10 illustrates an embodiment of some coded Profiles, and theirdescription, that can be used in Type III Request and Response.

FIG. 11 illustrates an embodiment of the Type IV speed-up techniqueaccording to the present invention.

DETAILED DESCRIPTION OF THE INVENTION

According to the present invention, techniques for telecommunicationsare provided. More particularly, the invention provides methods forreducing the time required to establish calls between terminals thatimplement the ITU-T H.324 Recommendation and other Standards andRecommendations derived from or related to this such as the 3G-324Mrecommendation developed and adopted by the Third Generation PartnershipProjects (3GPP and 3GPP2). More specifically, it relates to (i) a methodand apparatus for concatenating the H.245 messages that are required topass between the terminals at the start of the call to establish thecapabilities of both terminals and agree on the type and format of mediaand data to be exchanged (ii) a method and apparatus for usingnon-standard H.245 messages to accelerate such establishment (iii) amethod and apparatus of informing each terminal of the capabilities ofthe other and proposing the type and format of media and data to beexchanged by means of any user-defined fields that are inserted in thecall signaling protocol that is used for bearer establishment prior tothe start of the H.324 stage of the call, and (iv) a method andapparatus of informing each terminal of the capabilities of the otherand proposing the type and format of media and data to be exchanged bymeans of messages that are transmitted on the bearer channel prior tothe initiation of the H.324 Standard procedures. These methods may beused separately or severally to reduce the time that is taken from thepoint when a user requests the establishment of a call to the pointwhere media starts to be exchanged between the terminals. Merely by wayof example, the invention has been applied to the establishment ofmultimedia telecommunication between 3G-324M (H.324M based protocol)multimedia handsets on a mobile telecommunications network, and between3G-324M multimedia handsets and H.323 based terminals on a packetnetwork using a Multimedia Gateway to mediate between the protocols usedat each endpoint, but it would be recognized that the invention may alsoinclude other applications.

The methods described above are generic and can be implemented in manydifferent ways by a person skilled with the field. We describe belowexample embodiments to illustrate the methods which can be adaptedeasily to suite specific equipment needs.

Type I Example Embodiment

In a particular embodiment of this method of concatenated H.245 messagesa terminal combines H.245 Request Terminal Capabilities (TCS) andRequest Master Slave Determination (MSD) messages into a single H.245PDU. It also concatenates TCS and MSD Response Messages (Acks), multipleOpen Logical Channel Requests (OLC) and Multiplex Table Entry SendRequest (MES) in a single H.245 PDU. Finally it combines OLC and MESresponses into a third H.245 PDU. The process of setting up an H.324call between two terminals which support this embodiment of theconcatenation method is illustrated in FIG. 2. The result of adoptingthis approach reduces the number of round trips required for call setupfrom around ten to three. This embodiment requires that the MSDSE andCESE state machines can run in parallel, and that the multiple LCSE andMTSE state machines can run in parallel. This embodiment is merely oneexample of the application of the method of concatenated H.245 messagesin the present invention; other concatenations of messages can beconstructed; these may put different constraints on the signaling entitystate machines within the implementation of H.245.

Optionally, the method also includes reverting to a normal operation ifone of the terminals does not support Type I (i.e. concatenated H.245messages). The calling terminal in this case detects that because itwould not have received the H.245 response to the second of theconcatenated H.245 messages. In this case the calling terminal wouldrevert to individual H.245 messages in the SRP command frames andretransmit the H.245 messages individually from the second messageonwards. There can be many other variations, alternatives, andmodifications.

Alternatively, the method can also be applied to the Numbered SimpleRetransmission Protocol (numbered version of SRP which includes asequence number in the SRP command and SRP acknowledgement frames) andother like variations. Of course, there can be other variations,modifications, and alternatives.

Type II Example Embodiment

In a particular embodiment of the method of using custom H.245 messages,a non-standard Capability is used. An H.324-like equipment requires thatthe first H.245 message it sends is a Terminal Capability Set (TCS)message. The calling equipment includes a capability of typeNonStandardParameter in the TCS it sends to the answering equipment.This capability is identified by a NonStandardldentifier with a uniqueObject Identifier. This capability contains Equipment Preferences whichare the additional parameters needed by the called terminal to start thecall, including terminalType (needed for MSD in the same manner as it isrequired for standard H.245 operation) and Multiple Table Entry (MTE)Descriptors. FIG. 6 shows an example of an ASN.1 description containingthe syntax for all of these data. By including this NonStandardCapability, the calling party is required to accept the decision of thecalled party as to whether this method is used, and what channels areselected.

If the called equipment does not support this method the callingequipment receives a conventional TCSAck and normal H.245 negotiation isthen used to continue the call set-up.

If a called terminal receives a TCS containing the NonStandardcapability relating to this method and itself supports the method, itwill perform a master slave determination by comparing the terminalTypevalue in the received NonStandard capability with the value for thelocal terminal. The highest value will be selected as the master. In theevent of equal terminal type values, the calling terminal will beselected as the master.

The called terminal will analyze the received capability table andcapability descriptors to determine the OpenLogicalChannel and multiplextable entries for the new connection. The called terminal will respondwith a normal TCSAck if it cannot derive an acceptable channelconfiguration, or if it is unable to accept themultiplexEntryDescriptors provided. The remainder of the call set-upwill then be via normal H.245 negotiation.

If acceptable channel configurations and multiplex table entries can bederived, the called party will replace the normal TCSAck with an H.245ResponseMessage of the type NonStandardMessage. See FIG. 7 for an ASN.1Syntax description of the encoded data. The NonStandardIdentifier of thenon-standard response message will have the same Object Identifier asthe NonStandard capability which identifies this method.

Note that the called terminal does not include any additional orNonStandard capabilities into the TCS it sends to the calling terminal,even if it supports this method. The calling terminal must wait toreceive either a TCSAck or the NonStandardMessage before proceeding.

The process of setting up an H.324 call between two terminals whichsupport this embodiment of the method of using custom H.245 messages isillustrated in FIG. 3. This embodiment offers one and a half less roundtrip exchanges than the embodiment of the method of Concatenated H.245.

By embedding the Equipment Preferences as a NonStandard capability onthe TerminalCapabilitySet request message ensures that the calledterminal would not malfunction or hang-up as it is required to be ableto handle the case of a non-standard Capability being communicated toit.

The second key aspect is that the encapsulation of the custom message inthe TerminalCapabilitySet request message allows the terminal totransmit the custom message in the first H.245 message after the mobilelevel determination is done, and hence it does not have to wait.

The third aspect is that the TerminalCapabilitySet request containingthe Type II message embedded as a non-standard Capability can betransmitted using the Type I mode (together with one or more H.245messages).

The fourth aspect is that the called terminal responds with an Ackmessage that informs the calling terminal of the preferred modes of thecalled terminal and its selection of one of the preferred modes of thecalling terminal if the calling terminal presented several preferencesin its Type II message.

Type III Example Embodiment

In a particular embodiment of the method of using call signaling “user”information, Q.931 User-User Information Element is used in the SETUPand CONNECT PDUs. This Information Element is filled with an ASN.1encoded structure (See FIG. 8) including terminalType (needed for MSD inthe same manner as it is required for standard H.245 operation) and alist of profiles the calling terminal wishes to offer. By including thisInformation Element, the calling party is required to accept thedecision of the called party as to whether this method is used, and whatprofile is selected.

Each profile dictates the Mobile Level, Multiplex Table Entries, LogicalChannels used and codecs used for each Logical Channel. FIG. 10illustrates some examples of profiles. The profile contains all theinformation required to immediately begin a call and establish mediabetween the terminals without the need to go through further H.245signaling after the bearer is set up.

If the called terminal does not support this method, the callingterminal receives a Q.931 CONNECT PDU without a User-User InformationElement and normal call set-up is then used.

If a called terminal receives a SETUP PDU containing the User-UserInformation Element relating to this method and itself supports themethod, it will perform a master slave determination by comparing theterminalType value in the received Information Element with the valuefor the local terminal. The highest value will be selected as themaster. In the event of equal terminal type values, a technique such asselecting the calling terminal as the master can be used to resolve theconflict.

The called terminal will also select one of the offered profiles. Ifnone of the offered profiles are suitable then no User-User InformationElement should be added to the Q.931 CONNECT PDU, and the call proceedsas normal.

If a profile is suitable then the master slave determination result andthe selected profile is encoded according to the ASN.1 Syntax for theresponse and added to the Q.931 CONNECT PDU as a User-User InformationElement. FIG. 9 illustrates a particular embodiment.

The process of setting up an H.324 call between two terminals whichsupport this embodiment of the method of using call signaling “user”information is illustrated in FIG. 4.

Type IV Example Embodiment

The embodiment is illustrated in FIG. 11 where the Equipment Preferredmodes (Request and Response messages shown in FIG. 11) are transmittedon the bearer channel. The Equipment Preferred modes can be similar tothat described in the Type III embodiment section and can be an explicitdescription of preferred modes or a coded (index for look-up in a tableof common modes). With reference to FIG. 11, the Caller AF4 Requestmessage can be constructed according to the procedure below:

Type IV Requests and Responses Construction Procedure

Step A: Let S1=the Equipment Preferences message (explicit or coded suchas an index in a table). The Equipment Preferences include informationas described in the Type III technique and illustrated in FIG. 10. Themessage can be expressed as an encoded ASN.1 string or using anothersyntax.

Step B: Let S2=S1 encoded for error robustness. If no error coding isused then S2 is equal to S1.

Step C: Let S3=S2 framed with framing flag sequence for facilitatingdetection and synchronization. Note frame flag emulation in the S2 needsto be detected and protected. Protection can utilise a repetitionmechanism. For example if the framing flag is <f1><f2>, and an <f1><f2>occurs in S2, then the <f1><f2> is replaced by <f1><f2><f1><f2> by thetransmitted. The receiver will replace any received <f1><f2><f1><f2> by<f1><f2>. Note that if error encoding is used then this could besignaled by using a different set of framing flags in this procedure.

Step D: S4=S3 framed padded with framing flag sequence in order toextend the length of the string (number of octets) to a multiple of 160octets. This optional step is practical for 3G-324M implementation asthe transmission time slots typically correspond to 160 octets. Ifpadding is not important then S4 is same as S3.

The caller and answerer terminals transmit their Request messageconstructed as described above one or more times (typically a minimum of2) back to back (separated only by padding or synchronization andframing flags) in order to avoid cases where the first few octets of S4could have been lost because of bearer setup timing.

After the caller terminal transmits its preferred modes it expects aresponse or a conventional H.324-like initial bearer transmission ofthis method of session speed-up is not supported. What the answererfirst transmits on the bearer channel can be ignored by the caller andonly used by the caller to notice that the called (answerer) terminalsupports this method of session speed-up. The called terminal transmitsits response which incorporates the accepted mode of operation asdescribed in the Type III operation with the only difference being thatthe messages would be constructed according the construction procedureabove with the message being the response message.

Once the caller terminal receives the response it can start transmittingits media. The called terminal will be in position to accept media whenit has transmitted its response.

Note that the caller will be in a position to accept media according toits proposal when it transmits its request.

Note if the terminals do not recognize the messages or cannot detectthem (e.g. because of corruption) then they can proceed according toType II speed-up.

Embodiment in the Context of a H.324/H.323 Gateway:

A further embodiment demonstrating use with a gateway to an H.323terminal using “FastConnect” is illustrated by FIG. 5. These embodimentsoffer a maximum reduction in call set up time. These embodimentseliminate all round trip exchange for H.245 messages and, for the H.324call segment, initial mobile level detection.

Embodiment in the Context of a H.324/SIP Gateway:

The embodiment in this context is similar to that of the H.324/H.323gateway with the exception that the gateway converts the information(Type I, II, III and/or IV) to SIP signaling messages.

Additionally, any terminal may support Type III and another terminal maysupport Type I/II/IV. Both terminals should be able to operate at theircommon support type (i.e. in this case Type II) as if the callingterminal would not receive the Type III response in the call signalingphase. The general mode is that terminals fall back to the highestcommon mode and within that mode to the highest supported version. Ofcourse, there may be variations, alternatives, and modifications.

Although each of the above techniques has been described according tospecific techniques including Type I, Type II, Type III, and Type IV,there can be various modifications, alternatives, and variations. Thatis, one or more of the various types can be combined with other typesaccording to a specific embodiment. Additionally, a specific sequence ofmethods using certain types can be performed. As merely an example, amethod using Type III and then Type IV and then Type II and then Type Iand then a standard mode of operation can be performed. Alternatively,any combination of these types depending upon the application can alsobe performed according to specific embodiments. In a specificembodiment, Type II may be performed if Type III fails or is notsupported. Alternatively or in combination, Type I may be performed ifType II fails or is not supported. Any practical combination of thesemay be used depending upon a level of support for each of the terminalsaccording to a specific embodiment. In general, however, techniquesusing the call signaling process for embedding messages for the initialmode of operation may be performed before those techniques usingprocesses after call signaling has been established. Of course, one ofordinary skill in the art would recognize many variations,modifications, and alternatives.

The previous description of the preferred embodiment is provided toenable any person skilled in the art to make or use the presentinvention. The various modifications to these embodiments will bereadily apparent to those skilled in the art, and the generic principlesdefined herein may be applied to other embodiments without the use ofthe inventive faculty. Thus, the present invention is not intended to belimited to the embodiments shown herein but is to be accorded the widestscope consistent with the principles and novel features disclosedherein. For example, the functionality above may be combined or furtherseparated, depending upon the embodiment. Certain features may also beadded or removed. Additionally, the particular order of the featuresrecited is not specifically required in certain embodiments, althoughmay be important in others. The sequence of processes can be carried outin computer code and/or hardware depending upon the embodiment. Ofcourse, one of ordinary skill in the art would recognize many othervariations, modifications, and alternatives.

Additionally, it is also understood that the examples and embodimentsdescribed herein are for illustrative purposes only and that variousmodifications or changes in light thereof will be suggested to personsskilled in the art and are to be included within the spirit and purviewof this application and scope of the appended claims.

1. A method of processing a call between users with reduced call set-uptimes using one or more telecommunication networks, the method beingprovided between at least a pair of H.324-like terminals coupled to theone or more telecommunication networks, the method comprising: providingone or more preferences for a call associated with a first terminal anda second terminal, the one or more preferences being associated with aninitial mode of operation for the call between the first terminal andthe second terminal; processing the one or more preferences as a CustomMessage; establishing a bearer channel between the first terminal andthe second terminal after a call signaling process; transferring theCustom Message from the first terminal to the second terminal through atelecommunication network using the bearer channel; processing theCustom Message by the second terminal; transferring a Custom ResponseMessage by the second terminal using one or more response messages toindicate to the first terminal the initial mode of operation; andexchanging information between the first terminal and the secondterminal after the initial mode of operation has been established. 2.The method of claim 1 wherein the information comprises voice and video.3. The method of claim 1 wherein the information comprises voice.
 4. Themethod of claim 1 wherein the information comprises data.
 5. The methodof claim 1 wherein the information comprises video.
 6. The method ofclaim 1 wherein the one or more preferences is associated with an ITU-TASN.1 custom message.
 7. The method of claim 1 wherein the one or morepreferences is provided in a table, the table being stored in one ormore memories.
 8. The method of claim 1 wherein the one or morepreferences is coded as an index from a plurality of indices into atable of a plurality of predefined preferences modes, wherein the one ormore preferences is retrieved from the table by at least one of theterminals.
 9. The method of claim 1 wherein the first terminal is anH.324-like gateway.
 10. The method of claim 1 wherein the first terminalis selected from a H.324-like handset, H.324-like a gateway; or H.324like a server.
 11. The method of claim 1 wherein the second terminal isan H.324-like gateway.
 12. The method of claim 1 wherein the secondterminal is selected from a H.324-like handset, H.324-like a gateway, orH.325 a server.
 13. The method of claim 1 further comprising repeatingthe transferring of the Custom Message from the first terminal to thesecond terminal and processing the Custom Message by the second terminalfor at least N times, where N is 1 or greater; and repeatingtransferring of the Custom Response Message from the second terminal tothe first terminal for at least M times, where M is equal to N.
 14. Themethod of claim 1 wherein the Custom Response Message is an indicationthat at least one of the one or more preferences has been received bythe second terminal.
 15. The method of claim 14 wherein at least onepreference is a preferred mode of operation of the second terminal. 16.The method of claim 1 further comprising repeating the transferring ofthe Custom Message from the first terminal to the second terminal andprocessing the Custom Message by the second terminal for at least Ntimes, where N is 1 or greater, to enhance detectability of the one ormore preferences by the second terminal.
 17. The method of claim 1further comprising repeating the transferring of the Custom Message fromthe first terminal to the second terminal before the initial mode ofoperation has been established and processing the Custom Message by thesecond terminal for at least N times, where N is 1 or greater.
 18. Themethod of claim 1 further comprising establishing a standard mode ofoperation between the first terminal and the second terminal if theinitial mode of operation associated with the Custom Message has notbeen established between the first terminal and the second terminal. 19.A system for processing a call between users with reduced call set-uptimes using one or more telecommunication networks, the systemcomprising: one or more memories, the one or more memories comprising:code directed to providing one or more preferences for a call associatedwith a first terminal and a second terminal, the one or more preferencesbeing associated with an initial mode of operation for the call betweena first terminal and a second terminal; code directed to processing theone or more preferences as a Custom Message; code directed toestablishing a bearer channel between the first terminal and the secondterminal; and code directed to transferring the Custom Message from thefirst terminal to the second terminal through a telecommunicationnetwork using the bearer channel.
 20. The system of claim 19 wherein theone or more memories further comprises: code directed to processing theCustom Message by the second terminal; code directed to transferring aCustom Response Message by the second terminal using one or moreresponse messages to indicate to the first terminal the initial mode ofoperation.
 21. The system of claim 19 wherein the one or more memoriesfurther comprises: code directed to exchanging information between thefirst terminal and the second terminal after the initial mode ofoperation has been established.
 22. The system of claim 19 wherein thefirst terminal is selected from a H.324-like handset, H.324-like agateway, or H.324 like a server.
 23. The system of claim 19 wherein thefirst terminal is selected from a H.324-like handset, H.324-like agateway, or H.324 like a server.
 24. The system of claim 19 wherein theinformation comprises at least voice, data, or video.
 25. A method ofprocessing a call between users with reduced call set-up times using oneor more telecommunication networks, the method being provided between atleast a pair of H.324-like terminals coupled to the one or moretelecommunication networks, the method comprising: providing one or morepreferences for a call associated with a first terminal and a secondterminal, the one or more preferences being associated with an initialmode of operation for the call between the first terminal and the secondterminal; processing the one or more preferences as a Custom Message;establishing a bearer channel between the first terminal and the secondterminal; transferring the Custom Message using one or more messagesfrom the first terminal to the second terminal through atelecommunication network using the bearer channel; processing theCustom Message by the second terminal; accepting at least one preferencein the Custom Message by the second terminal; transferring a CustomResponse Message by the second terminal using one or more responsemessages to indicate to the first terminal that the initial mode ofoperation including the at least one preference has been accepted; andexchanging information between the first terminal and the secondterminal after the initial mode of operation has been established.
 26. Amethod of processing a call between users with reduced call set-up timesusing one or more telecommunication networks, the method being providedbetween at least a pair of H.324-like terminals coupled to the one ormore telecommunication networks, the method comprising: providing one ormore preferences for a call associated with a first terminal and asecond terminal, the one or more preferences being associated with aninitial mode of operation for the call between the first terminal andthe second terminal; processing the one or more preferences as a firstCustom Message; processing the one or more preferences as a secondCustom Message; establishing a bearer channel between the first terminaland the second terminal after a call signaling process; determiningwhether the first terminal or the second terminal becomes a decisionmaking terminal for selecting at least one preferred mode to be used bythe first terminal and the second terminal; identifying either the firstterminal or the second terminal as the decision making terminal whilethe other terminal becomes an accepting terminal; transferring the firstCustom Message from the decision making terminal to the acceptingterminal through a telecommunication network using the bearer channel;processing the first Custom Message by the accepting terminal;transferring the second Custom Message from the accepting terminal tothe decision making terminal through the telecommunication network usingthe bearer channel; accepting at least one preference in the secondCustom Message by the accepting terminal; exchanging information betweenthe decision making terminal and the accepting terminal after theinitial mode of operation has been established.
 27. The method of claim26 wherein the determining of the decision making terminal is providedby a pre-established process.
 28. The method of claim 27 wherein thepre-established process selects either the first terminal or the secondterminal as the decision making terminal.
 29. The method of claim 26wherein the determining of the decision making terminal is provided byinformation in the Custom Message.
 30. The method of claim 29 furthercomprising determining if a conflict exists in whether the firstterminal or the second terminal is the decision making terminal and thendetermining the decision making terminal by a pre-established process.31. A method of processing a call between users with reduced call set-uptimes using one or more telecommunication networks, the method beingprovided between at least a pair of H.324-like terminals coupled to theone or more telecommunication networks, the method comprising: providingone or more first preferences associated with a first preference modefor a call associated with a first terminal and a second terminal, theone or more first preferences being associated with an initial mode ofoperation for the call between the first terminal and the secondterminal; processing the one or more preferences as a first CustomMessage; embedding the first Custom Message in a predetermined field ofone or more messages of a call signaling message; establishing a bearerchannel between the first terminal and the second terminal: transferringthe first Custom Message from the first terminal to the second terminalthrough a telecommunication network using the bearer channel during acall signaling phase; processing the first Custom Message by the secondterminal; determining if the first Custom Message associated with thefirst preference mode is supported by the second terminal; andtransferring a first Custom Response Message by the second terminalusing a call signaling response message to the first terminal toindicate if the first preference mode has been accepted by the secondterminal.
 32. The method of claim 31 further comprising performing asecond process for call set up if the first preference mode is notrecognized or is not supported or has not been accepted by the secondterminal, the second process comprising: processing one or more secondpreferences associated with a second preference mode as a second CustomMessage; establishing a bearer channel between the first terminal andthe second terminal; transferring the second Custom Message from thefirst terminal to the second terminal through a telecommunicationnetwork using the bearer channel; processing the second Custom Messageby the second terminal; transferring a second Custom Response Message bythe second terminal using one or more second response messages to thefirst terminal to indicate if the second preference mode has beensupported by the second terminal.
 33. The method of claim 32 furthercomprising performing a third process for call set up if the secondpreference mode has not been supported by the second terminal, the thirdprocess comprising: processing one or more custom Non-Standard H.245messages or custom Non Standard fields in standard messages, the one ormore custom Non-Standard H.245 messages or custom Non-Standard fields instandard messages being associated with a third initial predeterminedmode of operation; transferring the one or more custom Non-StandardH.245 messages or custom Non Standard fields in standard messagesthrough a telecommunication network using the bearer channel from thefirst terminal to the second terminal; processing the one or more customNon-Standard H.245 messages or custom Non Standard fields in standardmessages by the second terminal; transferring a Custom Non-Standardresponse message associated with the one or more custom Non-StandardH.245 messages or custom Non-Standard fields in standard messages fromthe second terminal to the first terminal to indicate if the thirdinitial predetermined mode of operation has been supported by the secondterminal.
 34. The method of claim 33 further comprising performing afourth process for call set up if the third initial predetermined modeof operation has not been supported by the second terminal, the fourthprocess comprising: determining a common mobile level; determining twoor more H.245 messages associated with a set-up parameters for aninitial fourth predetermined mode of operation; concatenating the two ormore H.245 messages into at least one SRP frame, the one SRP frame beingcharacterized by a predetermined size of the SRP command frame;transmitting the SRP command frame, including the two H.245 messages,from the first terminal to the second terminal through atelecommunication network; and transmitting an SRP acknowledge messagefrom the second terminal to the first terminal indicate if the initialfourth predetermined mode of operation has been supported by the secondterminal.
 35. The method of claim 34 further comprising operating thefirst terminal and the second terminal in a standard mode of operationif the initial fourth predetermined mode of operation has not beensupported by the second terminal.
 36. A method of processing a callbetween users with reduced call set-up times using one or moretelecommunication networks, the method being provided between at least apair of H.324-like terminals coupled to the one or moretelecommunication networks, the method comprising: providing one or morepreferences for a call associated with a first terminal and a secondterminal, the one or more preferences being associated with an initialmode of operation for the call between the first terminal and the secondterminal; processing the one or more preferences as a Custom Message;establishing a bearer channel between the first terminal and the secondterminal after a call signaling process; transferring the Custom Messagefrom the first terminal to the second terminal through atelecommunication network using the bearer channel; processing theCustom Message by the second terminal; and exchanging informationbetween the first terminal and the second terminal after the initialmode of operation has been established.
 37. A method of initiating a setup process for a call between users with reduced set-up times using oneor more 3G telecommunication networks, the method being provided betweenat least a pair of H.324-like terminals coupled to the one or more 3Gtelecommunication networks, the method comprising: providing one or morepreferences for a call between a first terminal and a second terminal,the one or more preferences being associated with one or more modes ofoperation for the call between the first terminal and the secondterminal; processing the one or more preferences as a message;establishing a bearer channel between the first terminal and the secondterminal after a call signaling process; and transferring the messagefrom the first terminal to the second terminal through a portion of atelecommunication network using the bearer channel, the portion of thetelecommunication network being capable of transmitting at least voice,video, and data.
 38. The method of claim 37 wherein the one or moremodes of operation is predetermined.
 39. The method of claim 37 whereinthe one or more modes of operation is determined.
 40. The method ofclaim 37 wherein the one or more modes of operation is predefined. 41.The method of claim 37 wherein the one or more modes of operation isexplicit.
 42. The method of claim 37 wherein the one or more messages isone or more Custom messages.
 43. The method of claim 37 wherein the oneor more messages is one or more non-standard messages.
 44. The method ofclaim 37 wherein the one or more 3G networks is a 3GPP network.
 45. Themethod of claim 37 wherein the one or more 3G networks is a 3GPP2network.
 46. The method of claim 37 further comprising processing theone or more messages by the second terminal; and transferring one ormore response messages by the second terminal using one or more responsemessages to indicate to the first terminal the one or more modes ofoperation.
 47. The method of claim 46 further comprising exchanginginformation between the first terminal and the second terminal after aninitial mode of operation has been established.
 48. A system forprocessing a call between users with reduced call set-up times using oneor more telecommunication networks, the system comprising: one or morememories, the one or more memories comprising: code directed toproviding one or more preferences for a call associated with a firstterminal and a second terminal, the one or more preferences beingassociated with a predetermined mode of operation for the call between afirst terminal and a second terminal; code directed to processing theone or more preferences as a Custom Message; code directed toestablishing a bearer channel between the first terminal and the secondterminal; and code directed to transferring the Custom Message from thefirst terminal to the second terminal through a telecommunicationnetwork using the bearer channel.
 49. The system of claim 48 wherein theone or more memories further comprises: code directed to processing theCustom Message by the second terminal; and code directed to transferringa Custom Response Message by the second terminal using one or moreresponse messages to indicate to the first terminal the predeterminedmode of operation.
 50. The system of claim 48 wherein the one or morememories further comprises: code directed to exchanging informationbetween the first terminal and the second terminal after the initialmode of operation has been established.
 51. A method of processing acall between users with reduced call set-up times using one or moremobile telecommunication networks, the method being provided between atleast a pair of H.324-like terminals coupled to the one or more mobiletelecommunication networks, the method comprising: providing one or morepreferences for a call associated with a first terminal and a secondterminal, the one or more preferences being associated with apredetermined mode of operation for the call between the first terminaland the second terminal; processing the one or more preferences as amessage; establishing a bearer channel between the first terminal andthe second terminal after a call signaling process; and transferring themessage from the first terminal to the second terminal through atelecommunication network using the bearer channel.
 52. The method ofclaim 51 wherein the message is a Custom Message.
 53. The method ofclaim 52 further comprising processing the Custom Message by the secondterminal; and exchanging information between the first terminal and thesecond terminal after the initial mode of operation has beenestablished.
 54. A method of processing a call between users withreduced call set-up times using one or more telecommunication networks,the method being provided between at least a pair of H.324-liketerminals coupled to the one or more telecommunication networks, the oneor more telecommunication networks being capable of transferring atleast voice, video, and data, the method comprising: providing one ormore preferences for a call associated with a first 3G terminal and asecond 3G terminal, the one or more preferences being associated with apredetermined mode of operation for the call between the first 3Gterminal and the second 3G terminal; processing the one or morepreferences as a Custom Message; establishing a bearer channel betweenthe first 3G terminal and the second 3G terminal after a call signalingprocess; and transferring the Custom Message from the first 3G terminalto the second 3G terminal through a 3G telecommunication network usingthe bearer channel.
 55. A mobile communication terminal capable oftransferring at least voice, video, and data and processing a callbetween users with reduced call set-up times using one or moretelecommunication networks, the mobile communication terminal comprisingone or more computer memories, the one or more computer memoriesincluding: one or more codes directed to providing one or morepreferences for a call between the mobile communication terminal andanother terminal, the one or more preferences being associated with oneor more modes of operation for the call; one or more codes directed toprocessing the one or more preferences to provide at least one message;one or more codes directed to establishing a bearer channel between themobile communication terminal and the other terminal after a callsignaling process; and one or more codes directed to transferring themessage from the mobile communication terminal to the other terminalthrough at least a portion of a telecommunication network using thebearer channel, the portion of the telecommunication network beingcapable of transmitting at least data.
 56. The terminal of claim 55wherein the terminal is a mobile handset.
 57. The terminal of claim 55wherein the terminal is a gateway coupled to the 3G telecommunicationnetwork.
 58. The terminal of claim 55 wherein the one or more modes ofoperation is related to one or more predetermined modes of operation.59. The terminal of claim 55 wherein the terminal is terminal equipment.60. The terminal of claim 55 wherein the telecommunication network iscapable of transmitting voice and video.